Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add changelog entry for Dockerfile USER_GID as non root #11829

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

rogercoll
Copy link
Contributor

Description

This PR just adds a new changelog entry for the changes we are doing in the releases repository: open-telemetry/opentelemetry-collector-releases#738

The main reason is that the releases repository does not have any changelog mechanism, but the corresponding change is important enough to make the users aware of.

  • Is this the appropriate approach? Have there been any similar situations in the past?

My understanding is that this PR should be merged after open-telemetry/opentelemetry-collector-releases#738 but before its next release

Link to tracking issue

Fixes
open-telemetry/opentelemetry-collector-releases#662

change_type: 'enhancement'

# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
component: container
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no container component in this repo, maybe use release or image instead

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Replaced in 9593eba

Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

codecov bot commented Dec 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.58%. Comparing base (3f3e208) to head (9593eba).
Report is 92 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #11829   +/-   ##
=======================================
  Coverage   91.58%   91.58%           
=======================================
  Files         445      445           
  Lines       23737    23737           
=======================================
  Hits        21739    21739           
  Misses       1623     1623           
  Partials      375      375           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

component: image

# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
note: "Set Dockerfile's USER_GID as non root. OpenTelemetry Collector releases issue: https://github.com/open-telemetry/opentelemetry-collector-releases/issues/662"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] can you not add the link to the issues: field below?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, you can only link issues / PRs in this repo in issues:

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok 🤷🏼

@atoulme
Copy link
Contributor

atoulme commented Dec 11, 2024

You can add to the changelog of the release on opentelemetry-collector-releases, I don't think the opentelemetry-collector is the right place for this change entry.

@mx-psi
Copy link
Member

mx-psi commented Dec 11, 2024

I agree with Antoine, I think this change should be noted in the opentelemetry-collector-releases repository instead of here

@songy23
Copy link
Member

songy23 commented Dec 11, 2024

agree if we can changelog to the -releases repo, that would be more ideal

@atoulme
Copy link
Contributor

atoulme commented Dec 13, 2024

Changelog is in -releases now!

@rogercoll
Copy link
Contributor Author

Sounds good to me as well. The primary reason for adding the changelog entry in the collector's repository was to ensure visibility, particularly for environments that might be impacted.

Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants